Description
CDL object instances are created and registered with unique names. Object names can be explicit (specified by the user), or implicit (automatically generated). In the latter case, the name is not displayed and is only used internally. Object names are defaulted and are primarily used as a means of improving readability. Object names are also used to create default access function names, circuit pin labels, and manual connection names.
Legal names can have any length, and can contain any alphanumeric character, but must start with a letter. Circuits cannot contain two objects of the same type with the same name, but can contain two objects of different type with the same name. Names are case sensitive.
Objects are registered using their full name and this is actually created by pre-pending the object's parent circuits names. This is analogous to a typical filing system where objects have names in the same way that files do, but also have paths that uniquely identify them. In the case of filing systems the path reflects the parent directory structure; in the case of CDL, the paths reflect the parent circuit hierarchy. In both cases the path and name are required to uniquely identify the target.
Example
In the example below the transient store "A" will be registered with the full unique name "CctC/CctB/A". Its local name is "A", and its path is "CctC/CctB".
|
|
|
|
|
|
